| 1. | Read uncommitted ? permits dirty reads but not lost updates
未授权读取允许脏读取，但不允许更新丢失。 |
| 2. | Read committed read uncommitted
读取提交的结果 |
| 3. | When this option is set , it is possible to read uncommitted modifications , which are called dirty reads
设置此选项之后，可以读取未提交的修改，这种读取称为脏读。 |
| 4. | The lowest isolation level , read uncommitted , can retrieve data that has been modified but not committed by other transactions
最低隔离级别（未提交读）可能检索到其他事务已修改但未提交的数据。 |
| 5. | The lowest isolation level , read uncommitted , may retrieve data that has been modified but not committed by other transactions
最低隔离级别（未提交读）可以检索其他事务已经修改、但未提交的数据。 |
| 6. | All concurrency side effects can happen in read uncommitted , but there is no read locking or versioning , so overhead is minimized
未提交读可能发生所有的并发副作用，但是由于无需读取锁定或读取版本，因此开销达到最小化。 |
| 7. | All of the concurrency side effects can happen in read uncommitted , but there is no read locking or versioning , so overhead is minimized
在未提交读中，所有并发副作用都可能发生，但因为没有读取锁定或版本控制，所以开销最少。 |
| 8. | Locking and row versioning prevent users from reading uncommitted data and prevent multiple users from attempting to change the same data at the same time
锁定和行版本控制可以防止用户读取未提交的数据，还可以防止多个用户尝试同时更改同一数据。 |
| 9. | Transactions running at the read uncommitted level do not issue shared locks to prevent other transactions from modifying data read by the current transaction
在read uncommitted级别运行的事务，不会发出共享锁来防止其他事务修改当前事务读取的数据。 |
| 10. | Heap - optimized bulkload operations with concurrent scan , under these isolation levels : snapshot , read uncommitted , and read committed using row versioning
Hobt . bulk _ operation下列隔离级别下的优化堆大容量加载操作与并发扫描：快照、未提交读和使用行版本控制的已提交读。 |
